15 research outputs found

    Spem4mde : un mĂ©tamodĂšle et un environnement pour la modĂ©lisation et la mise en Ɠuvre assistĂ©e de processus IDM

    Get PDF
    With the emergence of MDE, many organizations have been starting to transform their traditional software development processes into model-driven processes. Kleppe and al. define a model-driven software development as “a process of developing software using different models on different levels of abstraction with (automated) transformations between these models”.While model-driven development processes – called MDE processes – have started to appear, a tool-supported Process Modeling Language (PML) for describing and enacting such processes is still lacking. The concepts of SPEM 2.0 are quite generic since they are supposed to allow describing any kind of software. However, SPEM 2.0 concepts do not succeed in capturing the exact nature of most activities and artifacts of model-driven development. In addition, another major weakness of SPEM 2.0 is the lack of concepts for process enactment.The objective of this thesis is threefold: (1) provide an extension of SPEM that reifies the MDE concepts; (2) provide a language dedicated to behavioral modeling of MDE processes; (3) provide a conceptual architecture of a PSEE (Process-centered Software Engineering Environment) that guides process designer at modeling phase and developers at enactment time.To validate our approach, a prototype of this PSEE is developed under the TOPCASED environment. This prototype provides a graphical editor for structural and behavioral modeling of MDE processes, and a process enactment engine based on process behavior models. We have also applied our approach to a significant case study: the UWE (UML-based Web Engineering) process, which is a MDE process dedicated to web applications development.L’avĂšnement de l’IDM (IngĂ©nierie DirigĂ©e par les ModĂšles) a suscitĂ© beaucoup d’intĂ©rĂȘt de la part des organisations qui de fait commencent Ă  transformer leur processus de dĂ©veloppement traditionnel en un processus de dĂ©veloppement dirigĂ© par les modĂšles, appelĂ© aussi processus IDM.Au moment oĂč ces processus commencent Ă  Ă©merger, nous notons l’absence d’un langage dĂ©diĂ© pour les modĂ©liser et les mettre en Ɠuvre. Le standard SPEM 2.0 propose des concepts gĂ©nĂ©riques qui sont supposĂ©s ĂȘtre capables de dĂ©crire tout type de processus logiciel. Cependant, les concepts de SPEM ne capturent pas la nature exacte des processus IDM. D’autre part, une autre insuffisance majeure de SPEM rĂ©side dans le fait qu’il n’intĂšgre pas les concepts relatifs Ă  la mise en Ɠuvre des processus.L’objectif de cette thĂšse est triple : (1) proposer une extension de SPEM dans laquelle les concepts centraux des processus IDM sont rĂ©ifiĂ©s ; (2) proposer un langage dĂ©diĂ© Ă  la modĂ©lisation comportementale des processus IDM ; (3) proposer une architecture conceptuelle d’un environnement logiciel d’aide Ă  la modĂ©lisation et Ă  la mise en Ɠuvre des processus IDM.Pour valider notre approche, un prototype a Ă©tĂ© dĂ©veloppĂ© sous l’environnement TOPCASED. Ce prototype fournit d’une part un Ă©diteur graphique pour la modĂ©lisation structurelle et comportementale des processus IDM et d’autre part un environnement de mise en Ɠuvre s’appuyant sur les modĂšles comportementaux des processus. Nous avons Ă©galement appliquĂ© notre approche Ă  une Ă©tude de cas significatif: le processus UWE (UML-based Web Engineering), qui est un processus IDM dĂ©diĂ© au dĂ©veloppement d’applications web

    Étude in vitro de l’effet antifalcĂ©miant des globules rouges et de l’activitĂ© antioxydante d’extraits de la poudre de racines de Maytenus senegalensis Lam (Celestraceae)

    Get PDF
    La drĂ©panocytose est une hĂ©moglobinopathie largement rĂ©pandue chez les populations africaines noires. Actuellement, trĂšs peu de traitements conventionnels existent sur le marchĂ©, d’oĂč le recours Ă  la mĂ©decine traditionnelle. Maytenus senegalensis est une plante prescrite par les tradipraticiens dans la prise en charge de la drĂ©panocytose. L’activitĂ© antifalcĂ©miante des extraits de la poudre de racines de Maytenus senegalensis a Ă©tĂ© Ă©tudiĂ©e dans ce travail. AprĂšs obtention de l’extrait hexanique par extraction Ă  l’aide d’un Soxhlet, le marc est macĂ©rĂ© dans de l’acĂ©tate d’éthyle puis dans du mĂ©thanol pour donner les extraits correspondants. L’activitĂ© des fractions a Ă©tĂ© Ă©valuĂ©e sur des drĂ©panocytes de type SS. Les activitĂ©s antifalcĂ©miantes les plus importantes ont Ă©tĂ© observĂ©es pour les fractions polaires du mĂ©thanol et de l’acĂ©tate d’éthyle avec des taux d’inversion de la falciformation respectivement de 77% et de 65% Ă  10 mg/mL. Les activitĂ©s antioxydantes de M. senegalensis (CI50 = 0,195 ± 0,004 mg/mL) et de l’acide ascorbique (CI50 = 0,078 ± 0,002 mg/mL) ont Ă©tĂ© dĂ©terminĂ©es. Les pouvoirs antioxydants (PA) montrent que l’activitĂ© antiradicalaire de l’acide ascorbique (PA = 12,85) est 2,5 fois meilleure que celle de M. senegalensis (PA = 5,14). Les rĂ©sultats de l’étude justifient l’utilisation traditionnelle des racines de Maytenus senegalensis dans la prise en charge de la drĂ©panocytose.Mots clĂ©s : HĂ©moglobine, drĂ©panocytose, Maytenus senegalensis, activitĂ© antifalcĂ©miante, stress oxydant, radicaux libres, activitĂ© antioxydante

    The evolving SARS-CoV-2 epidemic in Africa: Insights from rapidly expanding genomic surveillance

    Get PDF
    INTRODUCTION Investment in Africa over the past year with regard to severe acute respiratory syndrome coronavirus 2 (SARS-CoV-2) sequencing has led to a massive increase in the number of sequences, which, to date, exceeds 100,000 sequences generated to track the pandemic on the continent. These sequences have profoundly affected how public health officials in Africa have navigated the COVID-19 pandemic. RATIONALE We demonstrate how the first 100,000 SARS-CoV-2 sequences from Africa have helped monitor the epidemic on the continent, how genomic surveillance expanded over the course of the pandemic, and how we adapted our sequencing methods to deal with an evolving virus. Finally, we also examine how viral lineages have spread across the continent in a phylogeographic framework to gain insights into the underlying temporal and spatial transmission dynamics for several variants of concern (VOCs). RESULTS Our results indicate that the number of countries in Africa that can sequence the virus within their own borders is growing and that this is coupled with a shorter turnaround time from the time of sampling to sequence submission. Ongoing evolution necessitated the continual updating of primer sets, and, as a result, eight primer sets were designed in tandem with viral evolution and used to ensure effective sequencing of the virus. The pandemic unfolded through multiple waves of infection that were each driven by distinct genetic lineages, with B.1-like ancestral strains associated with the first pandemic wave of infections in 2020. Successive waves on the continent were fueled by different VOCs, with Alpha and Beta cocirculating in distinct spatial patterns during the second wave and Delta and Omicron affecting the whole continent during the third and fourth waves, respectively. Phylogeographic reconstruction points toward distinct differences in viral importation and exportation patterns associated with the Alpha, Beta, Delta, and Omicron variants and subvariants, when considering both Africa versus the rest of the world and viral dissemination within the continent. Our epidemiological and phylogenetic inferences therefore underscore the heterogeneous nature of the pandemic on the continent and highlight key insights and challenges, for instance, recognizing the limitations of low testing proportions. We also highlight the early warning capacity that genomic surveillance in Africa has had for the rest of the world with the detection of new lineages and variants, the most recent being the characterization of various Omicron subvariants. CONCLUSION Sustained investment for diagnostics and genomic surveillance in Africa is needed as the virus continues to evolve. This is important not only to help combat SARS-CoV-2 on the continent but also because it can be used as a platform to help address the many emerging and reemerging infectious disease threats in Africa. In particular, capacity building for local sequencing within countries or within the continent should be prioritized because this is generally associated with shorter turnaround times, providing the most benefit to local public health authorities tasked with pandemic response and mitigation and allowing for the fastest reaction to localized outbreaks. These investments are crucial for pandemic preparedness and response and will serve the health of the continent well into the 21st century

    Spem4mde : a metamodel and software environment for assisted modeling and enactment of MDE processes

    No full text
    L’avĂšnement de l’IDM (IngĂ©nierie DirigĂ©e par les ModĂšles) a suscitĂ© beaucoup d’intĂ©rĂȘt de la part des organisations qui de fait commencent Ă  transformer leur processus de dĂ©veloppement traditionnel en un processus de dĂ©veloppement dirigĂ© par les modĂšles, appelĂ© aussi processus IDM.Au moment oĂč ces processus commencent Ă  Ă©merger, nous notons l’absence d’un langage dĂ©diĂ© pour les modĂ©liser et les mettre en Ɠuvre. Le standard SPEM 2.0 propose des concepts gĂ©nĂ©riques qui sont supposĂ©s ĂȘtre capables de dĂ©crire tout type de processus logiciel. Cependant, les concepts de SPEM ne capturent pas la nature exacte des processus IDM. D’autre part, une autre insuffisance majeure de SPEM rĂ©side dans le fait qu’il n’intĂšgre pas les concepts relatifs Ă  la mise en Ɠuvre des processus.L’objectif de cette thĂšse est triple : (1) proposer une extension de SPEM dans laquelle les concepts centraux des processus IDM sont rĂ©ifiĂ©s ; (2) proposer un langage dĂ©diĂ© Ă  la modĂ©lisation comportementale des processus IDM ; (3) proposer une architecture conceptuelle d’un environnement logiciel d’aide Ă  la modĂ©lisation et Ă  la mise en Ɠuvre des processus IDM.Pour valider notre approche, un prototype a Ă©tĂ© dĂ©veloppĂ© sous l’environnement TOPCASED. Ce prototype fournit d’une part un Ă©diteur graphique pour la modĂ©lisation structurelle et comportementale des processus IDM et d’autre part un environnement de mise en Ɠuvre s’appuyant sur les modĂšles comportementaux des processus. Nous avons Ă©galement appliquĂ© notre approche Ă  une Ă©tude de cas significatif: le processus UWE (UML-based Web Engineering), qui est un processus IDM dĂ©diĂ© au dĂ©veloppement d’applications web.With the emergence of MDE, many organizations have been starting to transform their traditional software development processes into model-driven processes. Kleppe and al. define a model-driven software development as “a process of developing software using different models on different levels of abstraction with (automated) transformations between these models”.While model-driven development processes – called MDE processes – have started to appear, a tool-supported Process Modeling Language (PML) for describing and enacting such processes is still lacking. The concepts of SPEM 2.0 are quite generic since they are supposed to allow describing any kind of software. However, SPEM 2.0 concepts do not succeed in capturing the exact nature of most activities and artifacts of model-driven development. In addition, another major weakness of SPEM 2.0 is the lack of concepts for process enactment.The objective of this thesis is threefold: (1) provide an extension of SPEM that reifies the MDE concepts; (2) provide a language dedicated to behavioral modeling of MDE processes; (3) provide a conceptual architecture of a PSEE (Process-centered Software Engineering Environment) that guides process designer at modeling phase and developers at enactment time.To validate our approach, a prototype of this PSEE is developed under the TOPCASED environment. This prototype provides a graphical editor for structural and behavioral modeling of MDE processes, and a process enactment engine based on process behavior models. We have also applied our approach to a significant case study: the UWE (UML-based Web Engineering) process, which is a MDE process dedicated to web applications development

    SPEM4MDE (un mĂ©tamodĂšle et un environnement pour la modĂ©lisation et la mise en Ɠuvre assistĂ©e de processus IDM)

    No full text
    L avĂšnement de l IDM (IngĂ©nierie DirigĂ©e par les ModĂšles) a suscitĂ© beaucoup d intĂ©rĂȘt de la part des organisations qui de fait commencent Ă  transformer leur processus de dĂ©veloppement traditionnel en un processus de dĂ©veloppement dirigĂ© par les modĂšles, appelĂ© aussi processus IDM.Au moment oĂč ces processus commencent Ă  Ă©merger, nous notons l absence d un langage dĂ©diĂ© pour les modĂ©liser et les mettre en Ɠuvre. Le standard SPEM 2.0 propose des concepts gĂ©nĂ©riques qui sont supposĂ©s ĂȘtre capables de dĂ©crire tout type de processus logiciel. Cependant, les concepts de SPEM ne capturent pas la nature exacte des processus IDM. D autre part, une autre insuffisance majeure de SPEM rĂ©side dans le fait qu il n intĂšgre pas les concepts relatifs Ă  la mise en Ɠuvre des processus.L objectif de cette thĂšse est triple : (1) proposer une extension de SPEM dans laquelle les concepts centraux des processus IDM sont rĂ©ifiĂ©s ; (2) proposer un langage dĂ©diĂ© Ă  la modĂ©lisation comportementale des processus IDM ; (3) proposer une architecture conceptuelle d un environnement logiciel d aide Ă  la modĂ©lisation et Ă  la mise en Ɠuvre des processus IDM.Pour valider notre approche, un prototype a Ă©tĂ© dĂ©veloppĂ© sous l environnement TOPCASED. Ce prototype fournit d une part un Ă©diteur graphique pour la modĂ©lisation structurelle et comportementale des processus IDM et d autre part un environnement de mise en Ɠuvre s appuyant sur les modĂšles comportementaux des processus. Nous avons Ă©galement appliquĂ© notre approche Ă  une Ă©tude de cas significatif: le processus UWE (UML-based Web Engineering), qui est un processus IDM dĂ©diĂ© au dĂ©veloppement d applications web.With the emergence of MDE, many organizations have been starting to transform their traditional software development processes into model-driven processes. Kleppe and al. define a model-driven software development as a process of developing software using different models on different levels of abstraction with (automated) transformations between these models .While model-driven development processes called MDE processes have started to appear, a tool-supported Process Modeling Language (PML) for describing and enacting such processes is still lacking. The concepts of SPEM 2.0 are quite generic since they are supposed to allow describing any kind of software. However, SPEM 2.0 concepts do not succeed in capturing the exact nature of most activities and artifacts of model-driven development. In addition, another major weakness of SPEM 2.0 is the lack of concepts for process enactment.The objective of this thesis is threefold: (1) provide an extension of SPEM that reifies the MDE concepts; (2) provide a language dedicated to behavioral modeling of MDE processes; (3) provide a conceptual architecture of a PSEE (Process-centered Software Engineering Environment) that guides process designer at modeling phase and developers at enactment time.To validate our approach, a prototype of this PSEE is developed under the TOPCASED environment. This prototype provides a graphical editor for structural and behavioral modeling of MDE processes, and a process enactment engine based on process behavior models. We have also applied our approach to a significant case study: the UWE (UML-based Web Engineering) process, which is a MDE process dedicated to web applications development.TOULOUSE2-SCD-Bib. electronique (315559903) / SudocSudocFranceF

    Spem4mde : Un mĂ©tamodĂšle et un environnement pour la modĂ©lisation et la mise en Ɠuvre assistĂ©e de processus IDM

    No full text
    International audienceL'avĂšnement de l'IDM (IngĂ©nierie DirigĂ©e par les ModĂšles) a suscitĂ© beaucoup d'intĂ©rĂȘt de la part des organisations qui de fait commencent Ă  transformer leur processus de dĂ©veloppement traditionnel en un processus de dĂ©veloppement dirigĂ© par les modĂšles, appelĂ© aussi processus IDM. Au moment oĂč ces processus commencent Ă  Ă©merger, nous notons l'absence d'un langage dĂ©diĂ© pour les modĂ©liser et les mettre en oeuvre. Le standard SPEM 2.0 propose des concepts gĂ©nĂ©riques qui sont supposĂ©s ĂȘtre capables de dĂ©crire tout type de processus logiciel. Cependant, les concepts de SPEM ne capturent pas la nature exacte des processus IDM. D'autre part, une autre insuffisance majeure de SPEM rĂ©side dans le fait qu'il n'intĂšgre pas les concepts relatifs Ă  la mise en oeuvre des processus. L'objectif de ce travail est triple : (1) proposer une extension de SPEM dans laquelle les concepts centraux des processus IDM sont rĂ©ifiĂ©s ; (2) proposer un langage dĂ©diĂ© Ă  la modĂ©lisation comportementale des processus IDM ; (3) proposer une architecture conceptuelle d'un environnement logiciel d'aide Ă  la modĂ©lisation et Ă  la mise en oeuvre des processus IDM

    Using the SPEM 2.0 kind-based extension mechanism to define the SPEM4MDE metamodel

    No full text
    International audienceThe objective 1 of the OMG's standard SPEM is to propose shared concepts for describing software and even systems processes. The SPEM 2.0 metamodel proposes concepts that are quite generic to describe model-driven development processes. Indeed, the artifacts of those processes are essentially models and relationships between them are numerous (e.g. impact, matching, overlap and so on). We notice that is difficult to have a process modeling language that is suitable to define any kind of process including MDE ones. To overcome this lack, we propose in this paper an extension of SPEM4MDE based on the SPEM 2.0 kind-based extension mechanism. It allows process designer to refine SPEM concepts in order to define the model-driven processes. To illustrate our approach, the MDE-based VUML process for models composition has been used

    An Y MDE Approach for Enactable Software Process Models Generation

    Get PDF
    International audienceThe advent of MDE enabled to automate software development while reducing its production time. While software companies need continually to improve and customize their software processes, an automated approach to do so is still lacking. Most of those companies have an organizational process that is used whenever they have an upcoming development project. Reusing the same process for any development project is somehow inadequate. So, tailoring of such a process is necessary to fit organisational and operational companies’ needs. However, even if that tailored process can be used for a specific project, it still lacks resources needed for execution. In this short paper, we propose a Y model-based approach that allows tailoring software processes and generating enactable software process models by using models transformations. We defined metamodels to express models involved in those transformations. We illustrate our approach with an extract of the UWE Process which we adapt and instantiate for a development project with .Ne

    TAILORING AND INSTANTIATION OF MDE PROCESS MODELS: A Y MODEL-BASED APPROACH

    No full text
    The adoption of MDE in software development has drastically changed the way of developing software products. It gives a way of automating software development while reducing production time. While software companies need continually to improve and customize their software processes, a quick approach to do so is still lacking. Most of those companies have an organizational process that is used whenever they have an upcoming development project. Reusing the same process for any development project is somehow inadequate. So, tailoring of such a process is necessary to fit projects specificities. However, even if that tailored process can be used for a specific project, it still lacks information about resources needed for execution. In this article, we propose a Y model-based approach that allows tailoring a MDE process model and instantiating it for a specific project in the context of an organization. This approach is made possible by using models transformations. We defined metamodels to express the context and resources of a project. It results in a more optimal use of stakeholder’s roles and a better way of producing software. We illustrate our approach with the UWE Process in a context of a maintenance project with J2E

    A Pattern-based Process Management System to flexibly execute Collaborative Tasks

    Get PDF
    International audienceManaging collaborations during the execution of a process is complex and challenging, especially for managing the collaboration inside a task having multiple instances performed by various actors. Existing process management approaches propose either a rigid control for conducting such collaborative tasks or no control at all. Aiming at a more flexible way to execute and control multi-instance tasks, we investigate a solution based on late-binding mechanism to allow actors choosing dynamically suitable strategies to perform their collaboration. First, we propose a process modeling language which focuses on describing multi-instance tasks and their dynamic instances at execution time. Second, this language is then used to represent patterns capturing reusable collaboration strategies. A prototype of a pattern-based Process Management System has been developed to demonstrate the possible flexible execution of collaborative tasks
    corecore